Add ReleaseCandidate releases feature #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eCandidateVersion spec
andreslucena
changed the title
alecslupu
requested changes
Jul 19, 2024
|
|
||
| To update, follow these steps: | ||
|
|
||
| ### 1.1. Update your Gemfile |
There was a problem hiding this comment.
Since we have the policy of one Decidim version, has one ruby version, i would add here also the Upgrade ruby step
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Until now, the
decidim-releaserscript only was working for Patch versions (i.e. from v0.28.0 to v0.28.1).This PR introduces the feature to make Release Candidates using this same tool (i.e. from v0.29.0.dev to v0.29.0.rc1).
For doing that, what I've done is:
ReleasePatchVersion)ReleaseCandidateVersionclassReleaserUtilsmoduleAfter this is merged, the next iteration would be to have a new class from
ReleaseMinorVersion(from v0.29.0.rcX to v0.29.0)As it is specially tricky to actually run this script without making a release, I can confirm that I've used this to create the branches for:
To check that I didn't break anything with the
ReleasePatchVersionrefactor, I've used this to create the branches for:I think this is ready for a merge.